home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The 640 MEG Shareware Studio 2
/
The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO
/
info
/
dvtribs.zip
/
DV&TRIBS.DOC
next >
Wrap
Text File
|
1992-08-02
|
25KB
|
648 lines
TRIBBS & DESKVIEW 386 1:21:46 8/2/1992
=====================
TRIBBS/DESQVIEW SETUP PAGE: 1
INDEX:
Disclaimer.................................................1
Purpose....................................................2
System Requirements........................................2
DESQview 386...............................................2
TriBBS.....................................................2
Setting up QEMM............................................3
Setting up DESQview........................................3
TriBBS Node 1..............................................4
Node 1 Startup & Board Batch Files.........................5
TriBBS Node 2 Setup........................................6
Node 2 Startup & Board Batch Files.........................7
Running a Local Node.......................................8
Running Higher Speed Modems & DESQview.....................8
Running TriBBS, Doors inside DESQview......................9
Setting up DESQview to Autoload my BBS....................11
It Still Won't Run!.......................................12
Epilogue..................................................13
Please note! Any use of this doc file, in whole or in part, removes ALL
responsiblity from Randall Reimer should your system crash. In short, USE AT
YOUR OWN RISK!
TRIBBS/DESQVIEW SETUP PAGE: 2
Purpose:
~~~~~~~~
TriBBS ver 3.0 brought many new and exciting features, including multi-node
chats. The full power of TriBBS is not realized until it is ran in a multi-
tasking enviroment. This can include WINDOWS 3.x, OS/2, DESQview 386 or any
multi-tasker which can take advantage of the 80386's protected and virtual
8086 modes. Most sysops who multi-task will be using DESQview, although some
use WINDOWS and a few are now using OS/2.
This doc file is intended to show how to set up Quarterdeck's DESQview 386
and TriBBS. It is possibly not the best way to set it up, rather, it is
merely the way I run it.
PLEASE! Be sure you are able to properly set up TRIBBS BEFORE you try
multi-nodes! I will not - can not - explain every detail of TRIBBS, and the
doc file for TriBBS adequately explains setting it up.
REQUIREMENTS:
~~~~~~~~~~~~~
- DOS ver 2.x or higher. This can include Double Dos, PC-Dos, etc.
- 2 meg RAM. Any less and you're restricted to one node
- An 80386 or newer processor. SX will work.
- DESQVIEW 386. (I've not recieved xwindows yet!)
- Two seriel ports.
Be aware the PC does NOT support more than two com ports being used at the
same time! (Address conflicts). If you intend on running 3 or more user
nodes, you must either use a LAN or a intelligent multi-serial board such as
Digi-Board's Digi-Channel card. Apparently, MCA equipt PS/2s can support
more than 2 serial ports running simultaneously.
Also! You may need to use SHARE.EXE if you use dos 4 or 5. This should
prevent corruption of files. I do not use it.
DESQview 386:
~~~~~~~~~~~~~
DESQview 386 consists of two seperate programs, although a third - MANIFEST
- is frequently included. Manifest is not covered in this doc file. This
doc file covers DESQview ver 2.3, and QEMM ver 5.13.
DESQview is a multi-tasker - or for the purists, a task switcher. It
allows you to open a number of windows, each which can run almost any dos
application (including Windows 3.1) while running different programs
at the same time. DESQview will run on almost any XT, AT or clone.
QEMM is a 386 controller, it enables the 386's vitual 8086 and 32 bit
protected modes. It also controls DESQview's 386 features. Without QEMM,
DESQview's powers are limited.
TRIBBS:
~~~~~~~
TriBBS is a small, powerful, easy to set up BBS. When installed in a
multi-tasking enviroment, it supports multi-nodes, multi-node chats, and a
local access node, as well as it's single node features which include most of
the popular BBS features desired.
TRIBBS/DESQVIEW SETUP PAGE: 3
SETTING UP QEMM:
~~~~~~~~~~~~~~~~
You MUST consult your QEMM manual to properly set up QEMM, or at least run
OPTIMIZE. To try to explain it here would be almost impossible as each
computer setup varies. Furthermore, use of a ram disk or a disk cache, Dos
5, and ANY TSR will likely effect QEMM's setup. I include my CONFIG.SYS only
as an example - YOUR CONFIG.SYS WILL LIKELY BE DIFFERENT!
MY CONFIG.SYS:
DEVICE=C:\QEMM\qemm386.sys RAM
FILES=30
STACKS=0,0
Buffers=25
dos=high
Please note the FILES=30 line - this is important if you're planning on
including door games on your BBS. Some games open a number of files - I used
to use files=20 but found 30 was required just for 2 nodes if both were using
doors. The dos=high is for MS-DOS ver 5
If you have difficulties setting up QEMM, QUARTERDECK has technical support
available. Please consult the manuals.
SETTING UP DESQVIEW:
~~~~~~~~~~~~~~~~~~~~
Again, you'll simply have to refer to your manuals included with DESQview.
I can not anticipate your system. If you have difficulties setting up
DESQview, QUARTERDECK has free technical support availible.
DESQview is easily fine-tuned to run TriBBS - or other communications
programs. Assuming you have already set up DV, open a DOS window and run
DVSETUP. Select advanced setup by pressing enter. You should see a screen
similar to this:
Type the letter that corresponds
to the option you wish to change:
Auto Dialer A
Colors C
Keyboard K
Logical Drives L
Mouse M
Performance P
Video Monitor V
Window Positions W
Select P (Performance). You should see:
TRIBBS/DESQVIEW SETUP PAGE: 4
Task Processing Time (in Clock Ticks)
Foreground: 1
Background: 1
Memory Usage (in K)
Common Memory: 17
DOS Buffer for EMS: 2
Optimize communications? (Y/N): N
Allow swapping of programs? (Y/N): N
Manage printer contention? (Y/N): N
Clock Ticks: Setting this to higher numbers may cause jerkiness for your
users. But play around with this! I've used 2 and 2 or 2 and 1. But DON'T
SET THE BACKGROUND NUMBER HIGHER THAN THE FOREGROUND! This will disable DV's
ability to "steal" clock ticks from idle windows. Use 18 as the highest
number BOTH can add up to.
Optimizing communications seems to improve com port 2 but really doesn't seem
worth the effort.
Allow Swapping of programs: Communication programs - be they TriBBS or
anything else - should NEVER be swapped!
I do not own a printer, so I do not select Manage printer contention.
If you are having any difficulties or problems up to this point, please try
to resolve them before continuing. If neccessary, consult a friend or
Quarterdeck's support. If not, we can procede to set up TriBBS.
TRIBBS NODE 1:
~~~~~~~~~~~~~~
First, set up TriBBS as explained in the TRIBBS manual you recieved when you
registered TriBBS, or consult TRIBBS.DOC included with TriBBS. You may
select the total number of nodes you intend on running even if you are not
going to set them up soon. Be aware the PC does NOT support more than two
com ports being used at the same time! (Address conflicts). If you intend
on running 3 or more user nodes, you must either use a LAN or an intelligent
multi-serial board such as Digi-Boards Digi-Channel card.
After you've set up TriBBS node 1, (and it is working OUTSIDE DESQview, it is
time to set up a DV window for it. Load DV and select OPEN WINDOW. Then
select ADD A PROGRAM. Select OTHER as TriBBS is not included on the list.
You'll be prompted for the path, enter your TriBBS dir.
I've called my TriBBS node one TBBS. This is my setup:
TRIBBS/DESQVIEW SETUP PAGE: 5
Program Name............: TBBS
Keys to Use on Open Menu: R1 Memory Size (in K): 128
─────────────────────────────────────────────────────────────────────────────
Program...: bbs.bat
Parameters:
Directory.:
─────────────────────────────────────────────────────────────────────────────
Options:
Writes text directly to screen.......: [Y]
Displays graphics information........: [Y]
Virtualize text/graphics (Y,N,T).....: [Y]
Uses serial ports (Y,N,1,2)..........: [1]
Requires floppy diskette.............: [N]
After you've set up this screen, press <F1> rather than enter. My screen at
this point will display:
System Memory (in K).......: 0 Maximum Program Memory Size (in K)..: 565
Script Buffer Size.......: 1000 Maximum Expanded Memory Size (in K): 256
Text Pages: 4 Graphics Pages: 2 Initial Mode: Interrupts: 00 to FF
─────────────────────────────────────────────────────────────────────────────
Window Position:
Maximum Height: 25 Starting Height: 25 Starting Row...: 0
Maximum Width.: 80 Starting Width.: 80 Starting Column: 0
─────────────────────────────────────────────────────────────────────────────
Shared Program
Pathname..:
Data......:
─────────────────────────────────────────────────────────────────────────────
Close on exit (Y,N,blank)......: [N] Uses its own colors..............: [Y]
Allow Close Window command.....: [Y] Runs in background (Y,N,blank)...: [Y]
Uses math coprocessor..........: [N] Keyboard conflict (0-F)..........: [0]
Share CPU when foreground......: [Y] Share EGA when foreground/zoomed.: [Y]
Can be swapped out (Y,N,blank).: [N] Protection level (0-3)...........: [0]
The above setups have worked well for me with both TriBBS and RBBS, and
should work on most systems.
-The CLOSE ON EXIT should be set to no.
-RUNS IN BACKGROUND must be set to yes.
-Please remember to set the CAN BE SWAPPED OUT to NO! Swapping a
communications program to disk could prove ... interesting.
NODE 1 BATCH STARTUP & BOARD BATCH FILES:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
My system uses BBS.BAT as the batch file which runs upon opening the
window. It sets up and runs all the files etc needed for node 1 operation.
Your requirements may be different but use this as a guideline - it works
on my bbs. A rundown of each command follows the batch file:
TRIBBS/DESQVIEW SETUP PAGE: 6
dvansi
set dszlog=xfer-1.def
c:
cd \tritel
board
-Dvansi: This allows DESQview to display ANSI. TriBBS itself does not
need Dvansi to run, but utilities and door games may require it. Not using
an ansi emulator will not crash the bbs, Ansi screens will look like
gibberish without it. Your users won't notice it but you will!
-set dszlog=xfer-1.def: If you're running DSZ, and if you're using TRIMAIL
you are, you should include this statement if you're going multi-node. It
eliminates conflicts between the various nodes should two users access DSZ.
-You might need to include a line with PATH=(whatever you want in your
path), however I did not need it on my system.
The remainder of the batch file simply switches to the TriBBS dir and calls
BOARD.BAT.
BOARD.BAT is used to actually manage the bbs. My board.bat is as follows:
cd \tritel
if exist door.bat del door.bat
if exist event.bat del event.bat
if exist endbbs del endbbs
bbs /C1
If exist door.bat door
if exist event.bat event
if exist endbbs goto end
board
:end
-This is the same file used in non-DV operation. A complete rundown of
this file is in your TriBBS docs.
TRIBBS NODE 2 SETUP:
~~~~~~~~~~~~~~~~~~~~
First, set up TriBBS Node 2 setup as explained in the TRIBBS manual you
recieved when you registered TriBBS, or consult TRIBBS.DOC included with
TriBBS, in the MULTINODES section. Before trying to run node 2 in DESQview,
please get it running in DOS first. If it will not run there it won't likely
run inside DV. Please take your time here and if you require further
assistance call one of the TRIBBS support boards or a sysop running TRIBBS in
DESQview.
Again, we'll go over NODE 2's DESQview ADD PROGRAM screens. Both are as
follows for my setup:
TRIBBS/DESQVIEW SETUP PAGE: 7
Program Name............: TriBBS node 2
Keys to Use on Open Menu: R2 Memory Size (in K): 128
─────────────────────────────────────────────────────────────────────────────
Program...: bbs2.bat
Parameters:
Directory.:
─────────────────────────────────────────────────────────────────────────────
Options:
Writes text directly to screen.......: [Y]
Displays graphics information........: [Y]
Virtualize text/graphics (Y,N,T).....: [Y]
Uses serial ports (Y,N,1,2)..........: [2]
Requires floppy diskette.............: [N]
=============================================================================
System Memory (in K).......: 0 Maximum Program Memory Size (in K)..: 565
Script Buffer Size.......: 1000 Maximum Expanded Memory Size (in K): 256
Text Pages: 4 Graphics Pages: 2 Initial Mode: Interrupts: 00 to FF
─────────────────────────────────────────────────────────────────────────────
Window Position:
Maximum Height: 25 Starting Height: 25 Starting Row...: 0
Maximum Width.: 80 Starting Width.: 80 Starting Column: 0
─────────────────────────────────────────────────────────────────────────────
Shared Program
Pathname..:
Data......:
─────────────────────────────────────────────────────────────────────────────
Close on exit (Y,N,blank)......: [N] Uses its own colors..............: [Y]
Allow Close Window command.....: [Y] Runs in background (Y,N,blank)...: [Y]
Uses math coprocessor..........: [N] Keyboard conflict (0-F)..........: [0]
Share CPU when foreground......: [Y] Share EGA when foreground/zoomed.: [Y]
Can be swapped out (Y,N,blank).: [N] Protection level (0-3)...........: [0]
The above setups have worked well for me with both TriBBS and RBBS, and
should work on most systems.
-The CLOSE ON EXIT should be set to no.
-RUNS IN BACKGROUND must be set to yes.
-Please remember to set the CAN BE SWAPPED OUT to NO! Swapping a
communications program to disk could prove ... interesting.
NODE 2 BATCH STARTUP & BOARD BATCH FILES:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
My system uses BBS2.BAT as the batch file which runs upon opening the
window. It sets up and runs all the files etc needed for node 2 operation.
Your requirements may be different but use this as a guideline - it works
on my bbs. A rundown of each command follows the batch file:
dvansi
c:
set dszlog=xfer-2.def
cd \tritel2
board2
TRIBBS/DESQVIEW SETUP PAGE: 8
-Dvansi: Anytime you open ANY DESQview window which displays ANSI you must
include this. Using DEVICE=ANSI.SYS in your config.sys won't work in DV.
-Set dszlog=xfer-2.def: Include this line if you use DSZ as an external
protocol or use TRIMAIL.
-Again, you may require a PATH=(WHATEVER YOUR PATH IS) line in this.
BBS2.BAT calls up BOARD2.BAT which handles the BBS operation. MY
BOARD2.BAT is as follows:
echo off
cd \tritel2
if exist door.bat del door.bat
if exist event.bat del event.bat
if exist endbbs del endbbs
bbs /C2
If exist door.bat door
if exist event.bat event
if exist endbbs goto end
board2
:end
-Again, nothing new or exciting here.
RUNNING A LOCAL NODE IN DESQVIEW:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rather than going into great detail here, I'll simply point you to Mark
Goodwin's TRIBBS docs, which does a better job explaining this. Again,
you'll want to be able to run this in DOS before approaching DESQview.
Because of the operation of this node, I do not deem it neccessary to run
this node in the background - it is not really a communications program when
it is ran locally.
One glitch of the local node is it seems to reset the daily data contained
on the waiting for caller screen. This is not something I spend hours
worrying over, if it happens to you and you absolutely can not tolerate it,
get in touch with the TRIBBS support conference and pour out your woes.
Because I just use the LOCAL NODE (or node 3) for message access, I do not
even have a window dedicated to it, I just open a Dos window and run it as
follows:
CD \TRIBBS3
BBS /C0
I can not see much reason for confusion between DESQview and TRIBBS LOCAL
ACCESS, so I'll not go further into it.
RUNNING HIGHER SPEED MODEMS & DESQVIEW:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
There are several considerations when running higher speeds than 2400 in
DESQview with multinodes. At 14400 or even 9600, charactors may be lost if
you're switching screens or doing floppy disk access. There is a way around
this. You may simply try setting the clock ticks for your higher speed node
(assuming you have a high speed and a low speed node) higher. The best way
to remove any possiblity of error is to install 16550AN chip in your serial
card on each high speed com port. However, if no problems occur, you might
not want to worry about this.
TRIBBS/DESQVIEW SETUP PAGE: 9
The only other concern with higher speeds is you may need to lock your com
port. Simply adding
SET COM2=38400
to board2.bat would lock com port 2 at 38400. Most - not all - high speed
modems require locked ports.
RUNNING TRIBBS, DOORS INSIDE DESQVIEW:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Running doors inside DESQview may be tricky, especially if the door
programmer gave no thought to multi-node operations. Sometimes door games
simply will not run in a multi-node setup. Other times, should both users
access the same door, files can be corrupted or the game will simply do
strange things! Again, it all depends on each door game.
TRIBBS.DOC contains several excellent methods to rectify the above
problems. There is another method which I used while running RBBS and
transfered to TriBBS. This is simply using resources at hand to bar one user
access to a door game IF that door game hates multi-node access. (most do!)
Lets take ALAN DAVENPORT'S YANKEE TRADERS. It will not crash if both nodes
access it simultaneously, but it will get confusing to both users. Therefore
I want to prevent node 2 from accessing YT (Yankee Traders) while node 1 is
playing. Here's how I do it in my YT.BAT & YT1.BAT (Yankee traders batch
files for nodes 1 & 2):
YT.BAT (NODE 1):
cd \doors\yt
IF EXIST DORINFO2.DEF GOTO EXIT
copy c:\tritel\dorinfo1.def
yt dorinfo1.def
DEL DORINFO*.DEF
:EXIT
ECHO *************************************** > COM1
ECHO ** ** > COM1
ECHO ** OOOPS! NODE 2 IS PLAYING THIS ** > COM1
ECHO ** ** > COM1
ECHO ** DOOR GAME! PLEASE TRY AGAIN IN ** > COM1
ECHO ** ** > COM1
ECHO ** A FEW MINUTES ... SYSOP ** > COm1
ECHO ** ** > COm1
ECHO *************************************** > COM1
board
TRIBBS/DESQVIEW SETUP PAGE: 10
YT1.BAT (NODE 2):
cd \doors\yt1
IF EXIST DORINFO1.DEF GOTO EXIT
copy c:\tritel2\dorinfo1.def dorinfo2.def
yt dorinfo2.def 19200
DEL DORINFO*.DEF
board2
:EXIT
ECHO *************************************** > COM2
ECHO ** ** > COM2
ECHO ** OOOPS! NODE 1 IS PLAYING THIS ** > COM2
ECHO ** ** > COM2
ECHO ** DOOR GAME! PLEASE TRY AGAIN IN ** > COM2
ECHO ** ** > COM2
ECHO ** A FEW MINUTES ... SYSOP ** > COM2
ECHO ** ** > COM2
ECHO *************************************** > COM2
board2
-By copying the DORINFOx.DEF file to the door game dir, I can use the IF
EXIST line to search for it, and if it finds it, it will display the OOOPS
message and return to the bbs. However, you MUST ensure the DORINFOx.DEF
file IS DELETED when the user playing it quits the game - otherwise the
game will be inaccessable to the other node forever!
I use this type of batch file to control multi-node access to most door
games. It works well, but there is one more problem. WHAT IF A USER DROPS
CARRIER hanging the BBS? In most cases, the door game will catch it. Or
systems will use a WATCHDOG tp monitor the comport - some will even reboot
the window inside DESQview. Search your support bbs for these types of
utilities. Having a bbs hang because a user drops carrier is no fun, even if
the user simply couldn't prevent it.
Lets assume a user drops carrier in ALAN DAVENPORT'S Trade Wars ver 9.03,
which did not monitor the com port for carrier detect. You can prevent the
BBS from hanging by using a watch dog. So the caller logs off, the computer
reboots, and the bbs loads up. Great!
However, there is one more problem. The BBS is up again, but when the
next user tries to play YT, he finds sees the OOOPS message! Why? Because
YT.BAT (or YT2.BAT) didn't get a chance to delete the dorinfo file!
This can happen if a computer freezes as well, so pay attention, class!
We need to get rid of the DORINFO files, so we can simply include a line
into our BBS.BAT (NODE 1's startup batch file, remember?) saying:
del c:\doors\TW\dorinfo*.*
Including this in BOARD.BAT would slow down the bbs when returning from the
doors, so it must go into either your autoexec.bat or else into BBS.BAT (or
BBS2.BAT) So now my BBS.Bat looks like this:
TRIBBS/DESQVIEW SETUP PAGE: 11
dvansi
set dszlog=xfer-1.def
c:
del d:\doors\TW2\dorinfo*.*
del d:\doors\AWARs\dorinfo*.*
del d:\doors\FISH\dorinfo*.*
del d:\doors\GAL\dorinfo*.*
del d:\doors\TSE\dorinfo*.*
del d:\doors\BARONS\dorinfo*.*
del c:\doors\PIT\dorinfo*.*
del c:\doors\SID\*.pas
del c:\doors\YT\dorinfo*.*
del c:\doors\YT1\dorinfo*.*
del c:\doors\FOA\dorinfo*.*
del c:\doors\MAZE\dorinfo*.*
del c:\doors\BBS\dorinfo*.*
C:
cd \tritel
board
This delays node 1 startup a few seconds, but it works! Please note you
might use CALLERS.SYS or DOORS.SYS instead of DORINFOx.DEF, the principle
remains the same!
SETTING UP DESQVIEW TO AUTOLOAD MY BBS:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
One of the powerful features of DESQview is it's script or "learn"
fuctions. Please read the section on this in your DV manual, and create a
AUTOLOAD script for your BBS. You may need to do this several times until
it runs, but when it is properly set up according to the DESQview manual, it
should load your BBS node(s) when you startup DV automatically.
Once this is done we can finally modify our AUTOEXEC file to run DESQview
instead of TriBBS. This is done simply by adding DV to AUTOEXEC.BAT, as
demonstrated by my AUTOEXEC.BAT:
PATH C:\UTILS;C:\QEMM;C:;C:\tritel;C:\DV;F:\SK;f:\pckwik
c:\qemm\loadhi /r:3 stderr
prompt $p$g
dv
IT STILL WON'T RUN!:
~~~~~~~~~~~~~~~~~~~~
If you're having difficulty still, don't hesitate to ask for help on the
TRIBBS SUPPORT CONFERENCE, located on INTELEC, FIDO and TTN networks.
Alternately you may try contacting QUARTERDECK Support or any TriBBS support
board. Bare in mind the sysops may be busy and take a few days to get back
to you!
TRIBBS/DESQVIEW SETUP PAGE: 13
EPILOGUE:
~~~~~~~~~
TRIBBS, DESQVIEW, QEMM, YANKEE TRADERS, TRADEWARS, STDERR, DOUBLE DOS, MS-
DOS, PC-DOS, WINDOWS, OS/2, SIDROIDS, RBBS, PCKWIK, SK, are all copywrite of
thier repective rightsholders.
TRIBBS may be downloaded from any Support BBS or from:
THE LOBSTER BOUY......207-941-0805, Bangor, ME. 14400 V.32/HST
Please report any errors or feedback to:
RANDALL REIMER
TOPFUN................403-464-5253, Edmonton, AB, CANADA, 14400 V.32bis,
or via net mail on the TTN network.